home *** CD-ROM | disk | FTP | other *** search
- From: mh1@irz.inf.tu-dresden.de (Michael Hohmuth)
- Subject: seduid scripts
- Date: Wed, 17 Mar 93 15:30:55 MET
- Mime-Version: 1.0
-
- I just saw Simon talking about seduid scripts in a comp.sys.atari.st.tech
- article...
-
- When we discussed about whether '#!' interpretation should be done by the
- kernel or by the library, I think it was a consensus that it should
- be done by the library to prevent implementation of inconsistent file name
- translations ("#!/bin/sh" -> u:\bin\sh.ttp ?) into the kernel.
- However, I think we forgot the case of seduid-scripts which need some
- help by the kernel.
-
- I would still prefer not to have the filename translation in the kernel.
- I'd like to propose a way to achieve setuid-scripts capability:
-
- What about a system call similar to Pexec() that takes the name of an
- interpreter, the interpreter's additional parameters and the name of the
- script to run as its arguments? All file names the kernel needs would be
- passed to it in TOS form.
-
- The library's exec() would notice that something is a script (Pexec() returns
- ENOEXEC), read the first line, translate the interpreter's name to TOS
- format and issue an Pscript() call (or whatever it would be called).
- The kernel would examine the script and set the uid/gid attributes etc.
- accondingly.
-
- Comments?
-
- Michael
- --
- Internet: hohmuth@freia.inf.tu-dresden.de
-